…38)

Updates `parity-manifest.json` to reflect the 8-PR parity wave landed today.

`commands_covered` block extended with the new commands (now 35 total):
- 3 new executions subcommands (replay / verification-pending / verify) from PR #31
- 9 new agents commands (messaging primitive identity surface) from PR #28
- 4 new messages commands (messaging primitive lifecycle) from PR #29
- 2 new workers commands (list / delete) from PR #33
- 2 new `key webhook-secret` subcommands from PR #33
- `--send-at` flag on `cueapi fire` from PR #37 (in flight, depends on hosted #618)

`command_drift`:
- `cueapi create`: 6 new flags moved missing → covered (--require-payload-override, --required-keys, --delivery, --alerts, --catch-up, --verification, --on-success-fire). Only `--transport` remains in missing — flagged as refactor scope, not a simple flag-add.
- `cueapi update`: 9 new flags moved missing → covered. missing_flags now empty.
- `cueapi fire`: new entry capturing the 3 covered flags including --send-at.
- `cueapi executions get`: missing_display cleared (PR #589 ported in #26).
- `cueapi executions list`: 4 new filters moved missing → covered (no remaining gap).

`endpoints_missing`:
- All 8 entries from the seed manifest cleared except `POST /v1/worker/heartbeat`.
- That endpoint stays in missing with documented rationale: cueapi-worker is
  the canonical wrapper with proper heartbeat-loop semantics. Direct CLI
  registration is redundant. Decision documented in the manifest entry +
  cueapi workers group docstring.

`ported_pr_history`:
- 9 entries with merge timestamps, replacing the pre-port forward-looking
  notes.
- Each entry cross-references the cueapi-cli PR + the hosted PR (when
  applicable) + the merge timestamp for forensics.

`cli_version_at_audit`: bumped 0.1.x → 0.2.x to reflect the new surface
area.

`last_full_audit`: kept at 2026-05-04 (this update is the post-merge
snapshot of the 2026-05-04 audit, not a fresh audit).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

…2 + #683 parity) (#43)

Extends the existing fire command with two flags covering recently-shipped
server features. --send-at was already there from a prior port (#618).

  --exit-criteria (repeatable, max 20)
      §14 work-verification-light required-assertion keys (cueapi #632).
      Receiver MUST report values for every key under outcome.assertions;
      missing keys mark the execution verification_failed. Pass empty
      string '' once to opt out of cue-level required_assertions for this
      fire (server distinguishes [] = explicit opt-out from None = use
      cue-level).

  --idempotency-key (≤256 chars)
      Opaque dedup key (cueapi #683 Phase 2). Same key + same body within
      24h returns the cached execution; same key + different body returns
      409 idempotency_key_conflict.

Implementation pin (caught earlier on cueapi-python #33 + cueapi-mcp #29):
idempotency_key is a BODY field on cues fire, NOT the Idempotency-Key
header. Server's FireRequest schema diverges from the messaging primitive's
header-based idempotency. Help text + load-bearing test pin this so a
future refactor doesn't 'simplify' to header-based (which would silently
not work — server FireRequest is extra='forbid' for unknown body fields,
ignores headers in body parsing).

Tests added (3):
  - test_fire_help: pins all 5 flags appear in --help (--payload-override,
    --merge-strategy, --send-at, --exit-criteria, --idempotency-key)
  - test_fire_exit_criteria_repeatable_via_help: validates click parser
    accepts repeated --exit-criteria flags
  - test_fire_help_pins_idempotency_key_as_body_field: load-bearing pin
    against future header-refactor

185/185 tests pass (was 183; 2 new + parser-validation added inline).

Source: drift audit handoff/cueapi-package-drift-2026-05-06; Backlog
rows "Parity port: PR #632 → cueapi-cli" + "PR #683 not in backlog
(folded in same-day)". Triggered by cueapi-main confirming bandwidth
on cueapi-cli lane this session ([CC-CUEAPI-DOC-DEBT-CLOSED-DISCIPLINE-
CODIFIED]).

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>